Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

Ouborough Godstone (now Rooks Nest/Streete Court)

reference: 15/GOD Q4
name: Ouborough Godstone (now Rooks Nest/Streete Court)
tree-preservation-order: undefined
15/GOD
uprn
address-text: Ouborough Godstone (now Rooks Nest/Streete Court)
point: POINT (-0.048560 51.252800)
geometry: MULTIPOLYGON (((-0.050193 51.250840,-0.050067 51.250996,-0.049955 51.250963,-0.049939 51.251427,-0.049770 51.251970,-0.049751 51.252008,-0.048271 51.252082,-0.046511 51.252119,-0.046545 51.252726,-0.045443 51.252865,-0.045108 51.252878,-0.044840 51.252899,-0.044558 51.252893,-0.043851 51.252772,-0.043741 51.252783,-0.043842 51.253132,-0.043849 51.253374,-0.044014 51.253718,-0.044306 51.254195,-0.044501 51.254325,-0.044960 51.254515,-0.045831 51.253817,-0.046594 51.253385,-0.046890 51.253276,-0.047217 51.253255,-0.047599 51.253275,-0.047870 51.253317,-0.048474 51.253632,-0.048888 51.253741,-0.049429 51.253808,-0.049784 51.253824,-0.050165 51.253898,-0.050851 51.252759,-0.051026 51.252661,-0.052262 51.252747,-0.053260 51.252674,-0.053696 51.252604,-0.054478 51.252147,-0.054985 51.251723,-0.055304 51.251117,-0.055377 51.250997,-0.055772 51.250461,-0.055666 51.250417,-0.055613 51.250331,-0.055008 51.250239,-0.054911 51.250426,-0.055003 51.250897,-0.054952 51.251277,-0.054506 51.251790,-0.054100 51.252077,-0.053596 51.252348,-0.053086 51.252457,-0.052550 51.252501,-0.050988 51.252492,-0.050500 51.252248,-0.050392 51.251984,-0.050246 51.250866,-0.050193 51.250840)))
notes
organisation
felled-date
entry-date: 1953-01-02
start-date: 1953-01-02
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

How to improve Tandridge District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL